Skip to content

Add an RSS feed of new patterns, with ORCID author links#144

Merged
RichardLitt merged 1 commit into
mainfrom
rss-feed-with-orcid
Jun 3, 2026
Merged

Add an RSS feed of new patterns, with ORCID author links#144
RichardLitt merged 1 commit into
mainfrom
rss-feed-with-orcid

Conversation

@RichardLitt
Copy link
Copy Markdown
Member

@RichardLitt RichardLitt commented May 25, 2026

Builds on top of #142.

What this changes

The site now publishes an RSS feed of new patterns at /feed_rss_created.xml. RSS is the open standard that lets people add a website to a "feed reader" (Feedly, NetNewsWire, Inoreader, even some email clients) and get a notification whenever something new is published — like a podcast subscription, but for articles.

Each item in the feed includes:

  • The pattern's title and link.
  • The publication date (first time the pattern was added to the repo).
  • A one-line summary, taken from the first paragraph of the pattern.
  • Every author credited with a clickable link to their ORCID profile — so a reader who subscribes can hover over a name and jump straight to that researcher's full publication history on ORCID.org.

How readers find it

Three ways:

  1. A short "Stay in the loop" section on the home page, right under the patterns listing, with a "Subscribe" link.
  2. A subscribe line at the bottom of every author page (for example on /authors/ciara-flanagan/).
  3. Browser autodiscovery — when someone opens any pattern page in a feed-reader-aware browser or in a reader app, the feed shows up automatically as a "Subscribe" option. This is the standard way most RSS subscribers find feeds in 2026.

What this doesn't change

  • No changes to how you write or edit patterns. The feed reads the same authors: frontmatter and authors.yml that Make an index of authors #89 #141 introduced — you don't need to do anything new.
  • No changes to which authors have ORCIDs displayed; authors without an ORCID in authors.yml simply appear in the feed without a link, the same way they do on pattern pages.
  • The home page, the navigation, and pattern pages all look almost the same — the only visible change is the small "Stay in the loop" section on the home page.

One thing worth flagging to contributors

CONTRIBUTING.md has been updated to say this explicitly, but: a contributor's ORCID, if they provide one, will now travel further than before — it appears in every RSS item for every pattern they've co-authored, not just on the pattern page itself. It's still the same ORCID iD they're already publishing on their profile, and it's still optional, but it's worth being upfront about. Anyone uncomfortable with that can simply leave the orcid: field out of their entry.

What to click on the preview site

  • / — scroll past the patterns listing to "Stay in the loop"; click the RSS feed link.
  • /feed_rss_created.xml directly — this is the raw feed (XML). It's not designed for humans, but a quick check that it loads and that author names appear is reassuring.
  • /authors/ciara-flanagan/ — scroll to the bottom; the subscribe line is below the patterns list.
  • Open any pattern page in Firefox or a feed-reader app — the autodiscovery link means the reader will find the feed without you having to copy a URL.

Stacking

This PR stacks on top of #142, which stacks on top of #141. Please merge #141 first, then #142, then this one — once each is in, the next rebases automatically onto main.

Follow-ups (already filed as separate issues)

A pre-merge review surfaced three useful improvements that are bigger than this PR and are tracked separately so they don't block this one merging:

🤖 Generated with Claude Code

The feed lists each pattern by first-publication date and credits every
author with a clickable link to their ORCID profile. Subscribers can
find it via the Material-emitted autodiscovery <link> tag, the new
"Stay in the loop" section on the home README, or the subscribe line
on every author page.

How it works:

- mkdocs-rss-plugin (pinned in .config/requirements.txt) generates the
  feed; filenames are left at the plugin defaults so Material's hard-
  coded autodiscovery URLs resolve correctly.
- .config/hooks/authors.py enriches each pattern's page metadata so the
  plugin sees real author names and an ORCID-linked attribution body.
  After build, the same hook post-processes the generated XML for spec
  compliance: <author> → <dc:creator>, item-level <description> wrapped
  in CDATA so the ORCID anchor tags render in feed readers, the self-
  referencing <source> element dropped, and unescaped categories
  (e.g. "Education & Skills") re-escaped to keep the feed well-formed.
- authors.yml entries are now validated at build time. Slugs, names,
  affiliations, and ORCIDs must match strict regexes; any HTML-tag
  character in a name or affiliation fails the build. This closes a
  stored-XSS hole that would otherwise let a malicious PR inject script
  via author metadata.

Follow-ups to file as separate GitHub issues:

1. Broader feed coverage — per-tag feeds, an Atom variant, and a JSON
   Feed mirror so modern readers (NetNewsWire, Feedbin) have a
   first-class option.

2. Scholarly identifiers — DOIs per pattern via Zenodo, ROR IDs for
   affiliations, and surfacing both in the feed metadata so scholarly
   graph crawlers (OpenAlex, CrossRef) can ingest the catalogue.

3. Tests + UX iteration — unit tests for the authors hook (the
   pre-merge review surfaced concrete failure cases worth pinning),
   an RSS icon for the subscribe affordance, consistent wording across
   the three subscribe surfaces, and revisiting the per-author
   placement which currently sits below the patterns list.

Stacked on top of #141 (author pages) and #142 (ORCID iD icon).
@RichardLitt RichardLitt force-pushed the rss-feed-with-orcid branch from 8e1d2ee to 658fd82 Compare June 3, 2026 01:31
@RichardLitt RichardLitt changed the base branch from bulk-migrate-authors to main June 3, 2026 01:31
@RichardLitt RichardLitt merged commit d5d6fbb into main Jun 3, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant